[SIL] Do not drop inner ExtInfo while rebuilding FunctionTypes #21351
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@swift-ci please test |
|
It could be that nothing looks at the extInfo, inner or outer, or the function type we build here. |
|
Yeah, the way ExtInfo is used to carry state across SIL function type lowering is pretty haphazard and gross in general. It might be worth redoing it so that the ExtInfo in any intermediate function types is just completely ignored, and the SIL ExtInfo gets computed separately. |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is really a question in the form of a pull request. Why are we dropping the inner
ExtInfohere? This seems like a bug.